@Chuxel what's the best way to test this?

@bowdenk7 I believe the only way to test the auto-pick up is to merge it in. It will then be in the next build of the Remote - Contaners extension.

@chrmarti Is there another trick I'm not aware of?

Merging and bumping the vscode-dev-containers version so it gets picked up with next update to try it out

You could copy it into the current install of the vscode-remote-containers extension (that will be overwritten by the next update).

It's a manual change to vscode-remote-containers to pick up a new version of vscode-dev-containers. (Currently it's copying the NPM package from the GitHub Releases page to the vscode-remote-containers repo.)

@Chuxel When pushing a new version of vscode-dev-containers, you also need to push a tag, so the result is published on GitHub's Releases tab. There are many ways to do this, I find the easiest to be running npm version minor to do the version increment in package.json and add the tag. And then git push --follow-tags to push the change to package.json and the new tag.

Currently the tag is missing, I'll add that and then also update vscode-remote-containers. 👍

Angular actually has its own definition now, so I suspect we should just remove this one.

https://github.com/angular/angular/tree/master/.devcontainer

@Chuxel thanks for sharing :)